View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001845 | T99X171.00 SKB Eagle | SW Issue | public | 2023-12-06 17:05 | 2024-01-31 15:45 |
| Reporter | (ALTech) JunGyu Kim | Assigned To | (ALTech) JunGyu Kim | Due Date | 2023-12-22 17:50 |
| Priority | immediate | Severity | s4-minor | Reproducibility | random |
| Status | closed | Resolution | fixed | ||
| Summary | 0001845: [Smart3][OS10][VCS] tombstone in android.hardware.audio@2.0-service-droidlogic | ||||
| Description | Hi Jason, We are doing monkey test in VCS FW (15.541.301) to check several issue is occurring. Today, the tombstone was occurred as below. ============================================================================================================ Build fingerprint: 'SKB/BFX_AT100/BFX-AT100:10/QTT5.200429.010/15.541.301-20231204:userdebug/release-keys' Revision: '0' ABI: 'arm' Timestamp: 2023-12-06 12:14:40+0900 pid: 3501, tid: 5691, name: reader >>> /vendor/bin/hw/android.hardware.audio@2.0-service-droidlogic <<< uid: 1041 signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfc67f186 r0 fc67f182 r1 c7e0b5b0 r2 00000001 r3 f170d4e8 r4 f170ffc0 r5 00000003 r6 f1701018 r7 f192c67c r8 f160f208 r9 00000000 r10 ec20be14 r11 f1700380 ip f192dce8 sp ec20bdb8 lr f18c1817 pc f18c156e backtrace: #00 pc 0004856e /apex/com.android.runtime/lib/bionic/libc.so (je_extent_dalloc_wrapper+70) (BuildId: a82a8324059a3f30a292a0e928691aca) #01 pc 00039443 /apex/com.android.runtime/lib/bionic/libc.so (arena_decay_to_limit+414) (BuildId: a82a8324059a3f30a292a0e928691aca) #02 pc 00034dcb /apex/com.android.runtime/lib/bionic/libc.so (je_arena_extents_dirty_dalloc+214) (BuildId: a82a8324059a3f30a292a0e928691aca) #03 pc 00036a8d /apex/com.android.runtime/lib/bionic/libc.so (arena_dalloc_bin_locked_impl+440) (BuildId: a82a8324059a3f30a292a0e928691aca) #04 pc 000368cd /apex/com.android.runtime/lib/bionic/libc.so (je_arena_dalloc_bin_junked_locked+12) (BuildId: a82a8324059a3f30a292a0e928691aca) #05 pc 000563b1 /apex/com.android.runtime/lib/bionic/libc.so (je_tcache_bin_flush_small+832) (BuildId: a82a8324059a3f30a292a0e928691aca) #06 pc 00057839 /apex/com.android.runtime/lib/bionic/libc.so (tcache_destroy+44) (BuildId: a82a8324059a3f30a292a0e928691aca) #07 pc 00058b93 /apex/com.android.runtime/lib/bionic/libc.so (je_tsd_cleanup+54) (BuildId: a82a8324059a3f30a292a0e928691aca) #08 pc 000590d1 /apex/com.android.runtime/lib/bionic/libc.so (tsd_cleanup_wrapper+16) (BuildId: a82a8324059a3f30a292a0e928691aca) #09 pc 000a64e3 /apex/com.android.runtime/lib/bionic/libc.so (pthread_key_clean_all()+50) (BuildId: a82a8324059a3f30a292a0e928691aca) #10 pc 000a6145 /apex/com.android.runtime/lib/bionic/libc.so (pthread_exit+38) (BuildId: a82a8324059a3f30a292a0e928691aca) #11 pc 000a6089 /apex/com.android.runtime/lib/bionic/libc.so (__pthread_start(void*)+22) (BuildId: a82a8324059a3f30a292a0e928691aca) #12 pc 00060141 /apex/com.android.runtime/lib/bionic/libc.so (__start_thread+30) (BuildId: a82a8324059a3f30a292a0e928691aca) ============================================================================================================ Unfortunately, logcat was not captured. So we are checking log in tombstone and there are some strange log, so I request analysis. We were recording the aging screen, and when the tombstone occurred, Google Assistant was running. 1. Please check there is any problem with the do_input_standby command being called twice. ============================================================================================================ --------- tail end of log main 12-06 12:14:34.517 3501 24515 D audio_hw_primary: in_standby: enter: stream(0xf162c8c0) 12-06 12:14:34.517 3501 24515 D audio_hw_primary: do_input_standby(0xf162c8c0) in->standby = 1 12-06 12:14:34.517 3501 24515 D audio_hw_primary: in_standby: exit 12-06 12:14:34.536 3501 24515 D audio_hw_primary: in_standby: enter: stream(0xf162c8c0) 12-06 12:14:34.536 3501 24515 D audio_hw_primary: do_input_standby(0xf162c8c0) in->standby = 1 12-06 12:14:34.536 3501 24515 D audio_hw_primary: in_standby: exit 12-06 12:14:34.544 3501 24515 I audio_hw_primary: ++adev_create_audio_patch ============================================================================================================ 2. When I close Google Assistant in normal status, the following eagle_echo logs are output in one batch. ============================================================================================================ 12-06 17:46:08.241 3526 3618 D eagle_echo: [echo_set_parameters] floatDelayTime=0.160000, feedback_fac=38, live_fac=90 12-06 17:46:08.241 3526 3618 D eagle_echo: [echo_set_parameters] fNumFrames=7680.000000, sampleRate_=48000.000000, sampleCount=15360 12-06 17:46:08.241 3526 3618 D eagle_echo: [echo_set_parameters] bytePerSample=2, bytePerFrame=4 12-06 17:46:08.241 3526 3618 D eagle_echo: [echo_set_parameters] buf_capacity=30720 12-06 17:46:08.241 3526 3618 D eagle_echo: [release_echo_buffer] free(g_echo_para.echobuf) ============================================================================================================ However, in tombstone, only the release_echo_buffer log is suddenly being output. ============================================================================================================ 12-06 12:14:39.979 3501 10201 I audio_hw_primary: source 0 type=1 sink type =2 amk patch src=7 12-06 12:14:39.979 3501 10201 D audio_hw_primary: unregister_audio_patch: enter 12-06 12:14:39.979 3501 10201 D audio_hw_primary: unregister_audio_patch: exit 12-06 12:14:39.979 3501 10201 I audio_hw_primary: --adev_release_audio_patch: after releasing patch, patch sets will be: 12-06 12:14:40.000 3501 24515 D audio_hw_primary: adev_close_input_stream: enter: dev(0xf1675240) stream(0xf162c8c0) 12-06 12:14:40.000 3501 24515 D audio_hw_primary: in_standby: enter: stream(0xf162c8c0) 12-06 12:14:40.000 3501 24515 D audio_hw_primary: do_input_standby(0xf162c8c0) in->standby = 1 12-06 12:14:40.000 3501 24515 D audio_hw_primary: in_standby: exit 12-06 12:14:40.000 3501 24515 D eagle_echo: [release_echo_buffer] free(g_echo_para.echobuf) 12-06 12:14:40.000 3501 24515 D audio_hw_primary: adev_close_input_stream: exit ============================================================================================================ Can you find the cause of this log? Please help to find the cause of this tombstone. Thank you. Kim | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| User List |
(ALTech) SY Yoon , (ALTech) Younkwang Jung , (SW) Jacky Chiang , |
|---|
|
|
|
|
|
Hi Sam Strangely, these symptoms have not been observed by other manufacturers until now Please give me your analysis opinion on this Thank you YK.Jung |
|
|
Hi Sam, Although the tombstone content is not exactly the same, I found how to the tombstone occurs at android.hardware.audio@2.0-service-droidlogic through Google Assistant. A tombstone occurred within about 30 minutes of running the script below. ======================================================== while do input keyevent KEYCODE_HOME sleep 1 input keyevent KEYCODE_DPAD_RIGHT sleep 1 input keyevent KEYCODE_DPAD_RIGHT sleep 1 input keyevent KEYCODE_ASSIST sleep 1 done; ======================================================== The FW I tested is 15.541.30. The cause of this tombstone appears to be Google Assistant. Please analyze it. Please note, this issue is occurring only BFX-AT100. INTEK does not occurring this issue. Thank you. Kim |
|
|
Hi Sam, I have attached log and tombstone files. Please refer it. Thank you. Kim |
|
|
OK, let me try it. Thanks~~ |
|
|
Hi JunGyu, According to attached log and tombstone files, I find that it is related to the echo functions: "backtrace: #00 pc 000576e8 /vendor/lib/hw/audio.primary.amlogic.so (echo_process+200) (BuildId: fc3cb367d894d1f9d9b5c70ed3255775)" And it is crashed in "echo_process" function. I don't know why it needs to execute this function, maybe it's audio routing problem. I still figure it out. Thanks~ Sam |
|
|
Hi Sam The progress of the issue should be reported daily. So please update the progress by 5:00 PM(KT) Thank you YK.Jung |
|
|
Hi JunGyu, Younkwang, Do you use (or connect) an external MIC while testing? |
|
|
Hi Sam, I did not connect RCU through bluetooth. So when I reproduce this issue there is no external MIC. Thank you. Kim |
|
|
Hi JunGyu, Please use this test FW to verify: release_by_fxn/smart3_test/20231212_mantis1845/usb_bfx-at100_V15.541.31.zip I change the timing of calling echo_process from "AUDIO_DEVICE_IN_LINE" to "AUDIO_DEVICE_IN_BUILTIN_MIC". Thanks~ Sam |
|
|
Hi Sam. Thank you for support. We are testing your test FW through attached script. SKB QA is doing Monkey test with this script and they found this issue at this. To check quickly, could you please test it in your side? Additionally, please share your patch details. Thank you. Kim |
|
|
Hi Sam. We are testing it on two STBs, all STB's are occurring the same tombstone. I think it is not related your patch but in our history, this tombstone is not occurred never. To verify it, could you please build it again as below? Amlogic released test patch for hwcomposer. 1. Build test FW based on 15.541.32 2. Apply your patch 3. Apply Amlogic's patch -> Peter already applied and build it. (15.541.321) If possible, please build test FW based on 15.541.321 -> If not, please apply below amlogic's patch date tag information path jira 12/06 d507e75ddf2 Omx: add protect for mTsyncHandle vendor/amlogic/common BTFAML-1375 08/03 26c509f9345 vc: add protection to avoid panic common BTFAML-988 12/11 9f059cc58f6 SurfaceFlinger: fix layer leak frameworks/native BTFAML-1374 Thank you. Kim |
|
|
Hi Sam Please explain the cause of this issue analyzed so far and how to solve it I have to report to SKB Thank you YK.Jung |
|
|
Hi JunGyu, about https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1845#c14718 => @hardware/amlogic diff --git a/audio/audio_hal/audio_hw.c b/audio/audio_hal/audio_hw.c @@ -4500,7 +4500,7 @@ static ssize_t in_read(struct audio_stream_in *stream, void* buffer, size_t byte } DoDumpData(buffer, bytes, CC_DUMP_SRC_TYPE_INPUT); // Vas add start; for echo; samyang 20200921 - if (!(in->device & AUDIO_DEVICE_IN_LINE)) { + if (in->device & AUDIO_DEVICE_IN_BUILTIN_MIC) { if(is_echo_process_needed()) { echo_process(buffer, in_frames); } What do you mean "found this issue at this"? Do you have the same tombstone issue? Because according to https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1845#c14720 "tombstones.zip", it seems like other tomestone issues(hwcomposer). And I think this JIRA is for "android.hardware.audio@2.0-service-droidlogic". So, if it is another tomestone issue, avoiding confusing, could you create another JIRA for it? Thanks~ Sam |
|
|
Hi Younkwang, I think the cause of this jira-1845 is wrong timing to calling "echo_process" function.(if (!(in->device & AUDIO_DEVICE_IN_LINE)) ) So I change the timing to execute echo process("echo_process"): if (in->device & AUDIO_DEVICE_IN_BUILTIN_MIC). And because there are several possible causes of tombstone, do you think it's better to create another jira for different tombstones? Thanks~ Sam |
|
|
Hi Sam Not enough to explain to SKB What is echo_process? and When is the function called and what is its role? You said you changed the timing. What timing did you change it from? Please explain it in more detail Thank you YK.Jung |
|
|
Hi Sam, 1. https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1845#c14718 ==> Originally, this issue started from SKB QA. They are testing monkey test through BMT_Monkey_script.zip and they found "android.hardware.audio@2.0-service-droidlogic" tombstone. So I have asked you to test both sides of your patch to determine it is affect. 2. https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1845#c14720 ==> In your test FW, another tombstone (hwcomposer) is occurring. To check if your patch is causing side effects, I would like to test it after Amlogic recently applied some hwcomposer related fixes. If there is anything you don't understand, please tell me. Thank you. Kim |
|
|
Hi Younkwang, The echo process is a function to deal with the AUX MIC stream in when users connect a AUX MIC. But according to the current SW code base, this echo process function will be triggered when stream in without connecting AUX earphone. So somehow on your test confition, the echo process is triggered without MIC stream in, and the tombstone happens. For resolving it, I change the triggering condition to "when connect a AUX MIC" to avoid echo process triggered without MIC stream in. Thanks~ Sam |
|
|
Hi Sam, On your test FW, "android.hardware.audio@2.0-service-droidlogic" was occurred in 3 tombestones. I checked for a moment, "echo_process" could not be found on tombstones. Maybe there is another cause. I attached tombstone and log files. Please check it. Thank you. Kim |
|
|
|
|
|
Hi JunGyu, May I say the "echo process tombstone" issue is resolved? Then I'll check the log " 20231214.zip", and will build a test FW to test (depend on your command of https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1845#c14720: 1.sync to v15.541.35 code base 2.apply my patch 3.Apply Amlogic's patch). Thanks~ Sam |
|
|
Hi Sam, I'm not sure. I think the amount and time for testing was short. Did you test it? How about your test result? Anyway, please build a test FW you mentioned. Thank you. Kim |
|
|
Hi JunGyu, I've tested the issue(below FW, using BMT_Monkey_script.sh) for several hours, and there's no tombstone. Due to there are Openmax and audio hardware issues and no live TV on my enviroment, I think it might be related with live TV. So I suggest you to let Amlogic to check these tombstones. Also, I provide you the test FW I mentioned: release_by_fxn/smart3_test/20231214_mantis1845/usb_bfx-at100_V15.541.35.zip Thanks~ Sam |
|
|
Hi Sam, I checked the issue that occurred today, and according to the log, it seems to be related to echo_process. // tombstone_05 // logcat.log.0073 12-13 20:14:05.583 24917 31198 E audio_hw_primary: samtest, in_read, AUDIO_DEVICE_IN_BUILTIN_MIC 80000004, AUDIO_DEVICE_IN_BACK_MIC 80000080, AUDIO_DEVICE_IN_LINE 80008000, AUDIO_DEVICE_IN_BLUETOOTH_A2DP 80020000, AUDIO_DEVICE_IN_BLUETOOTH_BLE 84000000 12-13 20:14:05.584 24917 31198 E audio_hw_primary: samtest, in_read, in->device 4, samtest_count 0 12-13 20:14:05.584 24917 31198 E audio_hw_primary: samtest, in_read, get is_echo_process_needed // After 3 seconds, crash was occurred 12-13 20:14:08.210 24917 24923 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfa6b16c6 in tid 24923 (HwBinder:24917_), pid 24917 (audio@2.0-servi) Since I don't know how the log was added, I can only guess, but please check this log. Thank you. Kim |
|
|
Hi JunGyu, If the tombstone is related to echo_process, it will occur at the same time, 3 seconds is very late. And also, the tombstone backtrace will show out: like: backtrace: #00 pc 000576e8 /vendor/lib/hw/audio.primary.amlogic.so (echo_process+200) (BuildId: fc3cb367d894d1f9d9b5c70ed3255775) So according to your log, it is not echo_process issue. Thanks~ Sam |
|
|
Hi Sam. Thank you for analyze. If so, there seem to be two causes. 1. Tombstone occurring in echo_process 2. Tombstone occurring for other reasons First, we will do test with the FW you provided until next monday to check if there are any tombstones occurring in echo_process. Please focus for tombstones that occur due to other causes. Thank you. Kim |
|
|
Hi Sam This issue has even been reported to SKB executives. The situation is getting worse. quick issue resolution is needed. Please update the progress by 3:00 PM(KT) today Thank you YK.Jung |
|
|
Hi Sam, We have tested your test FW / 15.541.34 (This FW is not included your test patch) last weekend. On both FW, there are many android.hardware.audio@2.0-service-droidlogic tombstone. But I can not find tombstone related "audio.primary.amlogic.so (echo_process+200)" So, I'm not sure your patch is effected. I would like to test again when fix other reasons cause the tombstone. Is there any update? Additionally, I uploaded logs and tombstones last weekend. https://drive.google.com/file/d/1zGbdpV7D7ev62nHej7Hj5RhXERi3akSG/view?usp=sharing Please check it. Thank you. Kim |
|
|
Hi Sam SKB is requesting a schedule to resolve this issue. Please let me know within an hour. Thank you YK.Jung |
|
|
Hi JunGyu, Younkwang, According to "20231214.zip" audio@2.0-service tombstone log: because all cases don't have a same cause(different backtraces), I can't find a pattern to debug. And I also don't know what problem position in the code, so it's difficult to add debugging log. For now, I only observe a weird point that there is a inport INPORT_BUILTIN_MIC log in "BFX-AT100_20231213-173541 > logcat.log.0073": 12-13 20:14:02.326 24917 24923 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) I want to know if your test enviroment includes connecting microphone and use it or not? Or what is that test scenario? Thanks~ Sam |
|
|
Hi Sam, We are not connected microphone. I attached test script. In this script, Google Assistant key will input randomly. RCU is not connecty via bluetooth but on test script, input Google Assistant key, I guess STB try to open MIC. Thank you. Kim |
|
|
Hi JunGyu, (1). I try it: 1.no connect MIC 2.unpair RCU 3.input keyevent KEYCODE_ASSIST. It will create a new audio patch with inport=INPORT_BUILTIN_MIC. (audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC)) And I think this is a problem because there actually no inport devices but a audio patch created. And I am affraid that Intek might not have problem in BMT with RCU paired. Could you please use their devices to verify again? (1.no connect MIC 2.unpair RCU 3.input keyevent KEYCODE_ASSIST) (2). I find that if I test it by press assist button(without pairing RCU), there will be a pair-reminding note pop up. But when I do test (1). using "input keyevent KEYCODE_ASSIST", the pair-reminding note won't pop up and the assist note "Try Saying..." will pop up. These two scenarios' behaviors are different. I think if you could let the M/W or APP team fix it, the "abnormally create audio patch" issue will disappear. Thanks~ Sam |
|
|
Hi Sam After RCU and STB are paired, press the Google Assistant key to send keycode=219. keycode=219 interceptKeyBeforeQueueing keycode : KEYCODE_ASSIST packageName In this case, MW does not handle it When RCU and STB are not paired, press the Google Assistant key to send keycode=394. keycode=394 When the STB receives this keycode, a pairing operation is worked. After pairing RCU and STB, we are proceeding with the test, but it seems that the issue has not been observed yet The test results are as follow STB 1: pairing is continuously connected and disconnected , Tombstone is not observed [Mon Dec 18 21:03:41 2023] atvr_remove: hdev->name = BMM_BA01_A6C removed, num 1->0 [Mon Dec 18 21:04:01 2023] atvr_probe:1998 [Mon Dec 18 21:04:01 2023] atvr_probe: name = BMM_BA01_A6C, vendor_id = 1767, product_id = 33027, num 0 [Mon Dec 18 21:04:01 2023] atvr_probe: Found target remote BMM_BA01_A6C [Mon Dec 18 21:04:01 2023] atvr_probe: remotes count 0->1 .. [Tue Dec 19 09:25:38 2023] atvr_probe: name = BMM_BA01_A6C, vendor_id = 1767, product_id = 33027, num 0 [Tue Dec 19 09:25:38 2023] atvr_probe: Found target remote BMM_BA01_A6C [Tue Dec 19 09:25:38 2023] atvr_probe: remotes count 0->1 .. STB 2: pairing is continuously connected and disconnected , Finally, the pairing was disconnected and the tombstone was observed. [Mon Dec 18 20:37:14 2023] atvr_remove: hdev->name = BRM_BA02_0BB removed, num 1->0 [Mon Dec 18 20:37:18 2023] atvr_probe:1998 [Mon Dec 18 20:37:18 2023] atvr_probe: name = BRM_BA02_0BB, vendor_id = 93, product_id = 2, num 0 [Mon Dec 18 20:37:18 2023] atvr_probe: Found target remote BRM_BA02_0BB [Mon Dec 18 20:37:18 2023] atvr_probe: remotes count 0->1 .. [Mon Dec 18 23:29:21 2023] atvr_probe: name = BMM_BA03_0BF, vendor_id = 93, product_id = 4, num 0 [Mon Dec 18 23:29:21 2023] atvr_probe: Found target remote BMM_BA03_0BF [Mon Dec 18 23:29:21 2023] atvr_probe: remotes count 0->1 [Mon Dec 18 23:29:21 2023] key down 304 [Mon Dec 18 23:30:29 2023] atvr_remove: hdev->name = BMM_BA03_0BF removed, num 1->0 <tombstone> Timestamp: 2023-12-19 05:08:49+0900 : STB 3: pairing is continuously connected and disconnected , Tombstone is not observed [Mon Dec 18 21:18:06 2023] atvr_remove: hdev->name = BRM_BA01_CB3 removed, num 1->0 [Mon Dec 18 21:18:25 2023] atvr_probe:1998 [Mon Dec 18 21:18:25 2023] atvr_probe: name = BRM_BA01_CB3, vendor_id = 1767, product_id = 33027, num 0 [Mon Dec 18 21:18:25 2023] atvr_probe: Found target remote BRM_BA01_CB3 [Mon Dec 18 21:18:25 2023] atvr_probe: remotes count 0->1 .. [Tue Dec 19 09:53:40 2023] atvr_probe: name = BRM_BA01_CB3, vendor_id = 1767, product_id = 33027, num 0 [Tue Dec 19 09:53:40 2023] atvr_probe: Found target remote BRM_BA01_CB3 [Tue Dec 19 09:53:40 2023] atvr_probe: remotes count 0->1 - The test results now show that the tombstone has not been observed since it was paired. (I need to check a little more time.) However, in the case of reporting like this, it is necessary to further review the status that the pairing is connected and disconnected. - In INTEK STB, tombstone is not generated even though no pairing state until now Thank you YK.Jung |
|
|
Hi Younkwang, JunGyu, I see~ Do you have whole logs of INTEK STB of this case(1.no connect MIC 2.unpair RCU 3.input keyevent KEYCODE_ASSIST.)? including these part but whole logcat logs: 12-18 17:21:09.151 3523 3606 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) 12-18 17:21:09.157 3523 8315 E audio_hw_primary: in_read: read failed - sleeping for buffer duration Thanks~ Sam |
|
|
Hi Sam, I have attached full log of intek box. I think the file below contains the log you're looking for. ================================================================================================ logcat.log.0001:141963:12-18 21:59:26.891 3522 3610 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0003:10937:12-18 21:32:09.959 3522 3610 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0004:134573:12-18 21:29:51.900 3522 4582 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0005:146426:12-18 21:19:53.870 3522 3522 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0006:137421:12-18 21:08:31.758 3522 3611 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0007:58913:12-18 20:50:25.264 3522 3610 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0007:60737:12-18 20:50:49.867 3522 3610 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0008:162207:12-18 20:48:01.488 3522 23309 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0010:20266:12-18 20:19:38.802 3522 3522 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0010:33336:12-18 20:20:29.079 3522 3522 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0011:118601:12-18 20:14:34.206 3522 8651 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0011:150729:12-18 20:17:05.503 3522 8651 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0012:7937:12-18 19:48:09.907 3522 4582 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) logcat.log.0013:109573:12-18 19:44:55.938 3522 3522 I audio_hw_primary: adev_create_audio_patch: device->mix patch: inport(INPORT_BUILTIN_MIC) ================================================================================================ Thank you. Kim |
|
|
Hi Sam, Note that I let you know the test result. 1. Without connect RCU in intek box 2. Remove KEYCODE_ASSIST and test it in eagle box On both cases, there are no tombstone occurred for 2 days. Please refer it. Thank you. Kim |
|
|
Hi Sam. Please update the progress of this issue. Thank you. Kim |
|
|
Hi Sam I don't have a meeting with SKB today. UI541 BMT will end(DEC/28) next week, but there is no solution yet. So I want to know the exact progress status of this issue. Please let me know about the current status ( Did you find the cause or not?.. etc.. ) Thank you YK.Jung |
|
|
Hi Younkwang, I find that if trigger google assistant without RCU paired, it will create a new audio patch to read audio stream. This will cause trouble sometimes. So now, I try to find a way not to create audio patch in this condition. Thanks~ Sam |
|
|
Hi Younkwang, JunGyu, About this tombstone issue(https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1845#c14763): Please use this FW /release_by_fxn/smart3_test/20231225_mantis1845/usb_bfx-at100_V15.541.35.zip to verify. We bypass the "KEYCODE_ASSIST" key if RCU unpaired. (to avoid create a new audio patch of inport device "INPORT_BUILTIN_MIC", this abnormal situation may cause tombstone). Thanks~ Sam |
|
|
Hi Sam, We are tested your test FW while 4~5 days, no tombstone occurred. It seems to have been fixed. Please apply this modification to the VCS / Hybrid branch. Thank you. Kim |
|
|
Hi JunGyu, What's the commit jira tag (BPM- or others...)? Thanks~ |
|
|
Hi Sam JIRA is https://jira.skbroadband.com/browse/BFXBTF-533 so Please use BFXBTF-533 Thank you YK.Jung |
|
|
done~, BFX-AT100_5.4.1 commit: 2024-01-02 12:08:11 | sam.cy.yang@mail.f.. | 8223cf20b78f | frameworks/base | [BFXBTF-533] 1845:fix tombstone by dropping KeyEvent.KEYCODE_ASSIST if RCU not paired BFX-AT100_5.4.1_VCS commit: 2024-01-02 12:06:06 | sam.cy.yang@mail.f.. | f962b237a332 | frameworks/base | [BFXBTF-533] 1845:fix tombstone by dropping KeyEvent.KEYCODE_ASSIST if RCU not paired |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-12-06 17:05 | (ALTech) JunGyu Kim | New Issue | |
| 2023-12-06 17:05 | (ALTech) JunGyu Kim | Status | new => assigned |
| 2023-12-06 17:05 | (ALTech) JunGyu Kim | Assigned To | => (SW) Jason Ling |
| 2023-12-06 17:05 | (ALTech) JunGyu Kim | File Added: tombstone_00.zip | |
| 2023-12-06 17:05 | (ALTech) JunGyu Kim | Issue Monitored: (ALTech) Younkwang Jung | |
| 2023-12-06 17:05 | (ALTech) JunGyu Kim | Issue Monitored: (ALTech) SY Yoon | |
| 2023-12-06 17:05 | (ALTech) JunGyu Kim | Priority | normal => high |
| 2023-12-06 17:41 |
|
Issue Monitored: (SW) Jason Ling | |
| 2023-12-06 17:41 |
|
Assigned To | (SW) Jason Ling => (SW) Sam Yang |
| 2023-12-06 17:46 |
|
Issue Monitored: (SW) Jacky Chiang | |
| 2023-12-08 15:13 | (ALTech) Younkwang Jung | Note Added: 0014688 | |
| 2023-12-11 09:39 | (ALTech) JunGyu Kim | Note Added: 0014694 | |
| 2023-12-11 09:40 | (ALTech) JunGyu Kim | Priority | high => urgent |
| 2023-12-11 09:53 | (ALTech) JunGyu Kim | Note Added: 0014695 | |
| 2023-12-11 09:53 | (ALTech) JunGyu Kim | File Added: 20231211.zip | |
| 2023-12-11 09:58 | (SW) Sam Yang | Note Added: 0014696 | |
| 2023-12-11 16:51 | (SW) Sam Yang | Note Added: 0014702 | |
| 2023-12-12 09:03 | (ALTech) Younkwang Jung | Note Added: 0014711 | |
| 2023-12-12 11:39 | (SW) Sam Yang | Note Added: 0014713 | |
| 2023-12-12 11:54 | (ALTech) JunGyu Kim | Note Added: 0014714 | |
| 2023-12-12 16:33 | (SW) Sam Yang | Note Added: 0014715 | |
| 2023-12-12 16:33 | (SW) Sam Yang | Issue Monitored: (SW) Sam Yang | |
| 2023-12-12 16:33 | (SW) Sam Yang | Assigned To | (SW) Sam Yang => (ALTech) JunGyu Kim |
| 2023-12-13 10:05 | (ALTech) JunGyu Kim | Note Added: 0014718 | |
| 2023-12-13 10:05 | (ALTech) JunGyu Kim | File Added: BMT_Monkey_script.zip | |
| 2023-12-13 13:28 | (ALTech) JunGyu Kim | Note Added: 0014720 | |
| 2023-12-13 13:28 | (ALTech) JunGyu Kim | File Added: tombstones.zip | |
| 2023-12-13 14:11 | (ALTech) Younkwang Jung | Note Added: 0014721 | |
| 2023-12-13 15:02 | (SW) Sam Yang | Note Added: 0014722 | |
| 2023-12-13 15:06 | (SW) Sam Yang | Note Edited: 0014722 | |
| 2023-12-13 15:13 | (SW) Sam Yang | Note Added: 0014723 | |
| 2023-12-13 15:31 | (ALTech) Younkwang Jung | Note Added: 0014724 | |
| 2023-12-13 15:48 | (ALTech) JunGyu Kim | Note Added: 0014725 | |
| 2023-12-13 15:48 | (ALTech) JunGyu Kim | Note Edited: 0014725 | |
| 2023-12-13 16:02 | (SW) Sam Yang | Note Added: 0014726 | |
| 2023-12-14 10:03 | (ALTech) JunGyu Kim | Note Added: 0014731 | |
| 2023-12-14 10:04 | (ALTech) JunGyu Kim | Note Added: 0014732 | |
| 2023-12-14 10:04 | (ALTech) JunGyu Kim | File Added: 20231214.zip | |
| 2023-12-14 13:55 | (SW) Sam Yang | Note Added: 0014735 | |
| 2023-12-14 15:34 | (ALTech) JunGyu Kim | Note Added: 0014737 | |
| 2023-12-14 17:08 | (SW) Sam Yang | Note Added: 0014738 | |
| 2023-12-14 17:10 | (ALTech) JunGyu Kim | Note Added: 0014739 | |
| 2023-12-15 09:22 | (SW) Sam Yang | Note Added: 0014744 | |
| 2023-12-15 10:40 | (ALTech) JunGyu Kim | Note Added: 0014746 | |
| 2023-12-18 11:10 | (ALTech) Younkwang Jung | Note Added: 0014750 | |
| 2023-12-18 12:34 | (ALTech) JunGyu Kim | Note Added: 0014752 | |
| 2023-12-18 13:17 | (ALTech) Younkwang Jung | Note Added: 0014754 | |
| 2023-12-18 13:18 | (ALTech) Younkwang Jung | Priority | urgent => immediate |
| 2023-12-18 14:08 | (SW) Sam Yang | Note Added: 0014755 | |
| 2023-12-18 14:25 | (ALTech) JunGyu Kim | Note Added: 0014757 | |
| 2023-12-18 14:25 | (ALTech) JunGyu Kim | File Added: BMT_Monkey_script-2.zip | |
| 2023-12-18 16:15 | (SW) Sam Yang | Note Added: 0014763 | |
| 2023-12-19 08:44 | (ALTech) Younkwang Jung | Due Date | 2023-12-08 17:50 => 2023-12-22 17:50 |
| 2023-12-19 12:35 | (ALTech) Younkwang Jung | Note Added: 0014771 | |
| 2023-12-19 14:53 | (SW) Sam Yang | Note Added: 0014773 | |
| 2023-12-19 14:53 | (SW) Sam Yang | Note Edited: 0014773 | |
| 2023-12-19 17:49 | (ALTech) JunGyu Kim | Note Added: 0014775 | |
| 2023-12-19 17:49 | (ALTech) JunGyu Kim | File Added: BID-AT200_20231218-192845.zip | |
| 2023-12-20 08:42 | (ALTech) JunGyu Kim | Note Added: 0014776 | |
| 2023-12-21 11:54 | (ALTech) JunGyu Kim | Note Added: 0014796 | |
| 2023-12-22 09:44 | (ALTech) Younkwang Jung | Note Added: 0014805 | |
| 2023-12-22 12:02 | (SW) Sam Yang | Note Added: 0014806 | |
| 2023-12-25 11:29 | (SW) Sam Yang | Note Added: 0014810 | |
| 2024-01-02 10:42 | (ALTech) JunGyu Kim | Note Added: 0014836 | |
| 2024-01-02 11:42 | (SW) Sam Yang | Note Added: 0014837 | |
| 2024-01-02 11:50 | (ALTech) Younkwang Jung | Note Added: 0014838 | |
| 2024-01-02 12:10 | (SW) Sam Yang | Note Added: 0014839 | |
| 2024-01-02 13:43 | (SW) Sam Yang | Note Edited: 0014839 | |
| 2024-01-31 15:45 | (ALTech) JunGyu Kim | Status | assigned => closed |
| 2024-01-31 15:45 | (ALTech) JunGyu Kim | Resolution | open => fixed |
